QRZ! Ham Radio 4/QRZ Ham Radio Callsign Database - Volume 4.iso/digests/tcp/940067.txt

Internet Message Format | 1994-11-13 | 8KB

Date: Mon, 14 Mar 94 04:30:01 PST
From: Advanced Amateur Radio Networking Group <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: TCP-Group Digest V94 #67
To: tcp-group-digest


TCP-Group Digest            Mon, 14 Mar 94       Volume 94 : Issue   67

Today's Topics:
                                 help

Send Replies or notes for publication to: <[e-mail]>.
Subscription requests to <[e-mail]>.
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: Mon, 14 Mar 1994 09:07:44 EST
From: [e-mail]
Subject: help
To: [e-mail]

add [e-mail]  tcp-group

------------------------------

Date: Mon Mar 14 01:56:14 MST 1994
From: [e-mail]
>From smtp Sat Mar 12 07:42 MST 1994 remote from zeus
Received: from ucsd.edu by ns.Novell.COM (4.1/SMI-4.1)
    id AA12996; Sat, 12 Mar 94 07:47:39 MST
Received: from localhost by ucsd.edu; id EAA05183
    sendmail 8.6.4/UCSD-2.2-sun
    Sat, 12 Mar 1994 04:30:16 -0800 for tcp-digest-list
Received: from localhost by ucsd.edu; id EAA05134
    sendmail 8.6.4/UCSD-2.2-sun
    Sat, 12 Mar 1994 04:30:05 -0800 for tcp-group-ddist
Errors-To: [e-mail]
Message-Id: <[e-mail]>
Date: Sat, 12 Mar 94 04:30:02 PST
From: Advanced Amateur Radio Networking Group <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Content-Length: 6132
Content-Type: text
Precedence: Bulk
Subject: TCP-Group Digest V94 #66
To: [e-mail]


TCP-Group Digest            Sat, 12 Mar 94       Volume 94 : Issue   66

Today's Topics:
                 Answer to DE <--> KISS mode problem
                              jnos 1.10a

Send Replies or notes for publication to: <[e-mail]>.
Subscription requests to <[e-mail]>.
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: Fri, 11 Mar 94 12:28:28 PST
From: [e-mail] (Steven Bible)
Subject: Answer to DE <--> KISS mode problem
To: [e-mail]

Thanks to all who replied to my question.  For those of you who may have
missed it here it is once again:

> How do you get the Kantronics Data Engine into Kiss mode for TCP/IP?
> I have tried INTERFACE KISS and RESET but the DE will transmit but
> not listen properly.  I cannot get anymore out of the documents.
> What am I missing. I am using NOS_1229.EXE PA0GRI version.
>
> Thanks, Steve N7HPR

Funny, I though I had asked a complete enough question to get a simple
answer.  How wrong I was.  Evan VE6EEI pointed out that I didn't
mention what serial port speed I was using.  As it turned out this
was one of two problems I was having.  See Evan's reply below.

The second problem was not setting the proper <params> in my
autoexec.nos file to pull RTS and DTR high.  Thanks to Kevin N0BEL
and Bob KA4BYP.

In summary:  Check the version of firmware you are using in the
Data Engine.  As it turned out I had version 1.06, an older version
that will not reliably communicate with the computer at greater than
9600 baud in KISS mode.  This version does work at 19200 in terminal
mode. Strange :-0.  Second, I added the line

   param ax0 RTS 1

to my autoexec.nos file and loaded up nos and everything worked!
Thanks abunch everyone!  This saved me a lot of head banging.
I did note that many other people had this same problem and had
wrestled with it for a long time before gaining the solution.

Here's some of the replies that help describe the problems others
have been having and their solutions.

73 Steve N7HPR ([e-mail])

--------------------- cut here ----------------------------------------

Evan [e-mail]

>Your doing it right.  What serial port speed are you using.  I found that
>v1.06 would drop characters at >9600 baud and caused problems, however
>v2.0 works great at 19200 on the serial port.  I have 3 de's running at
>different sites around the city with no problems.

>One thing to try is do a hard reset and reset the DE (ie. pull battery
>jumper.)  It may have gone off into la la land.

>ps: v1.06 and v2.0 are the de firmware.  I also use 2 128K static ram chips
>in all DE.  It gives the DE more buffer space.

>My next project for this summer is to burn some JNOS 4.0 v1.0 eproms and get
>jnos running inside the DE instead of the computer.

-----

Kevin N0BEL < [e-mail]>

>By "transmit" do you mean PTT transmit, or RS232 transmit (which would be
>received data).

>I assume that the problem you are having is that you are not receiving any
>data from the DE.

>I bet it is the RTS pin on the DE that is being held low.  This would prevent
>the DE from sending data from the DE to the PC.  RTS is controlled from the
>PC to facilitate handshake.

>JNOS has a 'param <iface> RTS 1' command, to force RTS to an on state.  Maybe
>GRI has the same thing.  If not, just make sure that it is high through some
>hardware method.

>If all else fails, try turning hardware handshaking off on the DE.  I think
>its in there somewhere.

>I have used the Data Engine since it first came out.  I have had very little
>problem with it.  If you start running 9600 or 19200 modem on it, you will
>have to make sure that hardware handshake (CTS) in the PC to DE direction
>works properly.  I have found that you will definately overrun the DE unless
>you do that.

>Also, my expriments show that an interface baud rate of 19200 or 38400 are
>pretty useless on the DE, even with handshake, the DE drops characters.

-----

Clint KA7OEI <[e-mail]>

>Keep in mind the KISS modem used by the DE is not perfectly "standard" since
>the upper nybble of one of the header bytes is used to tell the DE the whichh
>channel the data is to go and likewise, from whence data from the DE came...

-----

Tim AA5DF <[e-mail]>

>I have a Data Engine working in KISS mode here. All I did was to place the
>(9600) modem I wanted to use in port 0. I really don't think I needed to
>do this because I believe the DE uses the port that was selected at time
>of the reset to use while in KISS mode (I'm using just plain vanilla KISS
>here so the second port is not being used). I then did the INT KISS and
>power cycled the DE.

-----

Bob KA4BYP  <[e-mail]>

>I had the same problem for a long time with the DE.  I somehow discovered
>that flow control was necessary.  These are lines from my autoexec file
>that work for me:

 attach asy 0x3f8 4 ax25 p1 4096 256 19200 f  #comm1 as interface p1
 #>> lots of lines<<
 param p1 dtr 1
 param p1 rts 1
 #>> again more lines <<
 attach kiss p1 1 p2     #second kiss port as interface p2

>That will run both ports in the DE in kiss mode.  You of course must use
>the DE command PORTS 1 first to put it into 2 port mode.  Then set
>INTERFACE to KISS then do a RESET before running your NOS.

-----

end of message

------------------------------

Date: Fri, 11 Mar 94 12:35:32 PST
From: "(Johan. K. Reinalda)" <[e-mail]>
Subject: jnos 1.10a
To: [e-mail]

I've updated ucsd.edu and
ftp.ece.orst.edu...

Johan.

------------------------------

End of TCP-Group Digest V94 #66
******************************

------------------------------

End of TCP-Group Digest V94 #67
******************************